KipSS v1

KipSS v1.0 – KISS over IP.

2000.01.30

This is the first release of a new program, KipSS. The program is an interface between a TNC and other programs. Its main target is UI frames and APRS in particular.

Installation. KipSS works in conjunction with APRSPLUS.EXE, the executable of APRS+SA. APRS+SA need not be installed to make KipSS run. However, the file APRS+1.zip is required and can be found at ftp://ftp.tapr.org/aprssig/winstuff/aprsplus. KipSS can run from the same directory that APRS+SA is installed from if present on your computer. If APRS+SA is not installed, copy the contents of APRS+1.zip to a new directory. Copy the contents of KipSS.ZIP to the same directory. Create a new shortcut to APRSPLUS.EXE with a command line of: aprsplus.exe 1m kipss. Or run the included KIPSS.BAT file. The file MSCOMM32.OCX is also required for KipSS to run. This should be in your Windows\System directory and is installed by Street Atlas USA. If you do not have this file, contact the author.

Below is a screen shot of KipSS.

Operation. Once KipSS has started, enter your appropriate serial port communications setting in the "Settings" slot. In the following slot, enter the appropriate commands to put your TNC into KISS mode. Note that the characters <CR> indicate to the program to insert a carriage
return in the outgoing data string sent to the
TNC> You must enter a callsign in the "Callsign" slot before the serial port will open. KipSS will attempt to determine all the current IP addresses of you machine in the "IP Address" slot. Or you can manually enter an IP Address. Click the "Open" button to open the serial port. If the port opens successfully, the button’s caption will change to "Close". Click the "Kiss On" button to put your TNC into KISS mode. Click the "Open TCP/IP" button to create a TCP/IP socket on your machine for KipSS to use. If a socket is successfully created, the button’s caption will change to "Close TCP/IP". Checking the "Auto-Start" option, will cause KipSS to automatically open the serial port, initiate KISS mode, and create the TCP/IP socket next time the program starts.

There are several digipeater function. First note, KipSS does not support WIDEn-n digipeating with this release but does support callsign substitution. The digipeating options are: 1) No digipeating. 2) Digipeating of your set ALIAS. 3) Local Wide – this is new digipeating concept where the program will digipeat all packet address to WIDE or WIDEn-n, but where the digipeated output will marked to not digipeat any further. Example: if the incoming path is APS200,WIDE3-3, KipSS will digipeat the WIDE and the resulting path will be APS200,KH2Z,LWIDE*. This assumes my callsign is KH2Z. And finally, 4) Digi-All where all packets are digipeated in the Local Wide construct, regardless of the packets path. The last 2 digipeater functions are intended for very specialized use, and in general, should not be used.

When running, KipSS does not show an Icon on the taskbar, but does show an Icon in the System Tray. Clicking on the icon will bring KipSS into view. Click the [X] in the upper right of the KipSS window, or pressing Esc., will cause KipSS to disappear from view.

Operation – once the program has been installed and configured, client programs can connect to the KipSS node via TCP/IP. Client programs can be local on the same computer or local area network, or can be remote across the Internet. KipSS does require a login sequence which consists of a callsign and an appropriately calculated number for security reasons. This sequence may change in future releases. Program developers can contact the author for instructions on calculating the login number.

Packets received, will show a packet header with port number, followed by a colon, and then the data portion of the packet. Client program send data in exactly the same format for transmission by the KipSS node. The following is an example of both received and/or transmitted data:

KH2Z>APS199,WIDE2-2/1:=3401.41N/11709.45WzPHG3660 APRS+SA

There is no need by client programs to first set a callsign, then an unproto TO, then an unproto PATH. All is done by a single packet.

All client programs connected to KipSS will appear on RF as if they had their own individual TNC, with their own callsign. Client programs can also control their own outgoing path.

APRS+SA v1.99 XT fully supports KipSS.

Brent